Skip to content

chore(deps): update overrides devalue to ^5.9.0 [security] - autoclosed - #67

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-devalue-vulnerability
Closed

chore(deps): update overrides devalue to ^5.9.0 [security] - autoclosed#67
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-devalue-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
devalue ^5.7.1^5.9.0 age confidence

Svelte devalue: DoS via sparse array deserialization

CVE-2026-42570 / GHSA-77vg-94rm-hx3p

More information

Details

devalue.parse could, due to quirks in some JavaScript engines, be convinced to allocate much more memory than was needed when deserializing sparse arrays, leading to excessive memory consumption.

Severity

  • CVSS Score: 7.5 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

sveltejs/devalue (devalue)

v5.9.0

Compare Source

Minor Changes
  • 07d6a38: feat: export filterArrayIndices, the array-index filtering used by the indicesOf stringify operation, so custom operations can reuse it instead of reimplementing it
  • 07d6a38: feat: add pluggable operations option to parse/unflatten, allowing customization of how values are constructed while reviving (e.g. cross-realm or foreign-runtime revival)
  • 5b53532: feat: add pluggable operations option to stringify/stringifyAsync, allowing customization of how values are introspected during serialization (e.g. side-effect-free or foreign-runtime serialization)

v5.8.2

Compare Source

Patch Changes
  • 48cc81f: fix: serialize DataView subviews with the correct byte offset and length
  • cd6da94: fix: resolve circular references through custom revivers when payload is already hydrated
  • 29a3382: fix: uneval now produces valid output for a repeated empty Map or Set
  • 8c0db06: fix: serialize Temporal values referenced more than once in uneval
  • 3770846: fix: emit valid JS for BigInt64Array and BigUint64Array in uneval
  • 756265a: fix: preserve shared-reference identity for Map keys in uneval
  • faa8a05: fix: emit uneval reconstructions before the statements that reference them
  • 06129ad: fix: do not grow sparse arrays by one slot in uneval

v5.8.1

Compare Source

Patch Changes
  • 206ca67: fix: force sparse arrays to allocate sparsely

v5.8.0

Compare Source

Minor Changes
  • c5115b0: feat: add stringifyAsync for async serialization

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Aug 6, 2026

Copy link
Copy Markdown

Deploying stackhacker-ui-web with  Cloudflare Pages  Cloudflare Pages

Latest commit: 4aff804
Status: ✅  Deploy successful!
Preview URL: https://50fe66ee.stackhacker-ui-web.pages.dev
Branch Preview URL: https://renovate-npm-devalue-vulnera.stackhacker-ui-web.pages.dev

View logs

@renovate
renovate Bot force-pushed the renovate/npm-devalue-vulnerability branch from ba0b89b to 4aff804 Compare August 6, 2026 05:42
@renovate renovate Bot changed the title chore(deps): update overrides devalue to ^5.9.0 [security] chore(deps): update overrides devalue to ^5.9.0 [security] - autoclosed Aug 6, 2026
@renovate renovate Bot closed this Aug 6, 2026
@renovate
renovate Bot deleted the renovate/npm-devalue-vulnerability branch August 6, 2026 07:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants